# File and folder layout

A Vox urbis site has the following folder hierarchy:

```
--+--assets/--+--css/
  |           |
  |           +--js/
  |           |
  |           +--sass/
  |           |
  |           +--webfonts/
  |
  +--images/
  |
  +--templates/
  |
  +--data/
  |
  +--config.toml
```

| item          | designation |
|---------------|-------------|
| `assets/`     | Static items (harness) of the HTML template. Served transtarently by the engine. |
| `images/`     | Static images used by the HTML template. Served transtarently by the engine.     |
| `templates/`  | Tera templates                                                                   |
| `data/`       | Local file data for the data driven pages                                        |
| `config.toml` | Site configuration file                                                          |

## `assets/` and `images/`

Contents of these hierarchies are served transparently by the engine.

There us no specific requirements to the contents of these folders; their layout shown on the above pic is solely for demonstrational purposes. 

## `templates/`

The hierarchy in this folder defines the hierarchy of the web site as seen in the browser.

* each filesystem folder becomes a folder in a http url path
* the engine serves default `index.html` if an url is a folder url (i.e. its path ending on `/`)
* the engine redirects to folder if a folder url was lacking trailing `/`

By convention, 

* the suffix of tera template file names should be `.html`
* the names of import-only templates should be prefixed with `_`